Skip to content

Fix jruby CI#3608

Merged
tenderlove merged 2 commits into
ruby:mainfrom
Earlopain:fix-jruby-ci
Jul 22, 2025
Merged

Fix jruby CI#3608
tenderlove merged 2 commits into
ruby:mainfrom
Earlopain:fix-jruby-ci

Conversation

@Earlopain

Copy link
Copy Markdown
Collaborator

The current version constraint is too specific and doesn't allow 10.0.1.0 which was recently released

The current version constraint is too specific and doesn't allow 10.0.1.0 which was recently released
@Earlopain

Copy link
Copy Markdown
Collaborator Author

Well, the tests run now but they look proper broken. Much stuff about missing constants. No idea what to do about that. Let me see if going back to 10.0.0.0 solves it

@Earlopain

Copy link
Copy Markdown
Collaborator Author

I pinned to 10.0.0.0 for now and opened an upstream issue at jruby/jruby#8923

@st0012 st0012 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah it looks like something (constant autoloading?) is off on the JRuby side. I think this is a fair mitigation while waiting for JRuby team's response.

@tenderlove
tenderlove merged commit 5ee83f5 into ruby:main Jul 22, 2025
58 checks passed
@Earlopain

Copy link
Copy Markdown
Collaborator Author

I tracked it down to autoloading with private_constant which prism does in a few places, reproduction in jruby issue.

@Earlopain
Earlopain deleted the fix-jruby-ci branch October 3, 2025 10:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants